Utilizing a transport protocol for fifth generation (5g) client devices to carry messages on wireline access

ABSTRACT

A device may utilize a point-to-point protocol over Ethernet (PPPoE) and a point-to-point protocol (PPP) to register the device with a core network, and may establish a first packet data unit (PDU) session with the core network based on the PPPoE and the PPP. The device may configure the first PDU session, based on the PPPoE and the PPP, to provide a first service, and may generate first keep alive messages to maintain the first PDU session. The device may establish a second PDU session with the core network based on the PPPoE and the PPP, and may configure the second PDU session based on the PPPoE and the PPP, where the second PDU session is configured to provide a second service that is different than the first service. The device may generate second keep alive messages to maintain the second PDU session.

BACKGROUND

A client device (e.g., a residential gateway, a user equipment (UE),and/or the like) may be connected to a fifth generation (5G) corenetwork using wireline access (e.g., transmission of information over aphysical element, such as a fiber optic able, a coaxial cable, a twistedpair cable, and/or the like). In such an arrangement, the client devicemay need to transmit non-access stratum (NAS) messages (e.g., packetdata units (PDUs)) on the wireline access when the client device isconnected to the 5G core network using the wireline access.

SUMMARY

According to some implementations, a method may include utilizing apoint-to-point protocol over Ethernet (PPPoE) and a point-to-pointprotocol (PPP) to register a device with a core network, andestablishing a first packet data unit (PDU) session with the corenetwork based on the PPPoE and the PPP. The method may includeconfiguring the first PDU session with the core network based on thePPPoE and the PPP, wherein the first PDU session may be configured toprovide a first service, and generating first keep alive messages tomaintain the first PDU session with the core network. The method mayinclude establishing a second PDU session with the core network based onthe PPPoE and the PPP, and configuring the second PDU session with thecore network based on the PPPoE and the PPP, wherein the second PDUsession may be configured to provide a second service that is differentthan the first service. The method may include generating second keepalive messages to maintain the second PDU session with the core network.

According to some implementations, a device may include one or morememories and one or more processors to utilize a PPPoE and a PPP toregister the device with a core network, and establish a first PDUsession with the core network based on the PPPoE and the PPP. The one ormore processors may configure the first PDU session with the corenetwork based on the PPPoE and the PPP, wherein the first PDU sessionmay be configured to provide a first service, and may establish a secondPDU session with the core network based on the PPPoE and the PPP. Theone or more processors may configure the second PDU session with thecore network based on the PPPoE and the PPP, wherein the second PDUsession may be configured to provide a second service that is differentthan the first service.

According to some implementations, a non-transitory computer-readablemedium may store one or more instructions that, when executed by one ormore processors of a device, may cause the one or more processors toutilize a PPPoE and a PPP to register the device with a core network,and establish a first PDU session with the core network based on thePPPoE and the PPP. The one or more instructions may cause the one ormore processors to configure the first PDU session with the core networkbased on the PPPoE and the PPP, wherein the first PDU session may beconfigured to provide a first service. The one or more instructions maycause the one or more processors to transmit first keep alive messagesto maintain the first PDU session with the core network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1S are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIGS. 3 and 4 are diagrams of example components of one or more devicesof FIG. 2.

FIGS. 5-7 are flow charts of example processes for utilizing a transportprotocol for 5G client devices to carry messages on wireline access.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

Currently, NAS messages may be transmitted via a single PDU sessionmodel or a multi-access PDU session model, and multiple (e.g., single ormulti-access) PDU sessions may be required for transmitting the NASmessages. Traffic for each PDU session may be destined for differentcore network devices and may require different services (e.g., anaggregate maximum bitrate, a guaranteed bitrate, quality of service(QoS) shaping requirements, and/or the like). However, identifyingdifferent PDU sessions from a same client device may not be achievableby using a media access control (MAC) address, an Internet protocol (IP)address, virtual local area networks (VLANs), and/or the like.

One current technique to handle different PDU sessions includes causingthe control plane to utilize an extensible authentication protocol (EAP)over PPPoE to transport NAS control plane packets. Unfortunately, sincethe EAP carries the NAS packets, the forwarding plane may be required toperform time consuming and resource intensive deep packet inspection toidentify packets to be provided to the control plane. The EAP is alwaysinitiated from the core network side and only a 5G-capable client devicemay respond to the EAP. Moreover, an EAP request that seeks to identify5G capabilities of the client devices will impact existing clientdevices that are EAP capable but not 5G capable.

Another current technique to handle different PDU sessions includescausing the data plane to utilize stateless PPPoE to transport the datapackets. In this technique, a session identifier is allocated by theclient device and a core network device blindly accepts the packet basedon the session identifier, which exposes the core network device topotential attacks. Furthermore, a combination of a MAC address and asession identifier from the client device will be insufficient touniquely identify a PDU session, and this technique requires expensivechanges to an access network of the core network.

Thus, current techniques to handle different PDU sessions may wastecomputing resources (e.g., processing resources, memory resources,communication resources, and/or the like), networking resources, and/orthe like associated with performing deep packet inspection, determining5G capability of a client device, modifying an access network, handlingnetwork attacks, and/or the like.

Some implementations described herein provide a client device thatutilizes a transport protocol to carry messages via wireline access to a5G core network. For example, the client device may utilize a PPPoE anda PPP to register the client device with a core network, and mayestablish a first PDU session with the core network based on the PPPoEand the PPP. The client device may configure the first PDU session withthe core network based on the PPPoE and the PPP, where the first PDUsession may be configured to provide a first service, and may generatefirst keep alive messages to maintain the first PDU session with thecore network. The client device may establish a second PDU session withthe core network based on the PPPoE and the PPP, and may configure thesecond PDU session with the core network based on the PPPoE and the PPP,where the second PDU session may be configured to provide a secondservice that is different than the first service. The client device maygenerate second keep alive messages to maintain the second PDU sessionwith the core network.

In this way, the client device may utilize a transport protocol to carrymessages via wireline access to a 5G core network. The client device mayutilize PPPoE and PPP with a new set of protocol identifiers for controltraffic (e.g., packets) and data traffic. The client device may utilizethe PPPoE and PPP to handle multiple PDU sessions and thus providedifferent services to the multiple PDU sessions, as required. This, inturn, conserves computing resources (e.g., processing resources, memoryresources, communication resources, and/or the like), networkingresources, and/or the like that would otherwise be wasted in performingdeep packet inspection, determining 5G capability of a client device,modifying an access network, handling network attacks, and/or the like.

FIGS. 1A-1S are diagrams of one or more example implementations 100described herein. As shown in FIG. 1A, a client device may be associatedwith a wireline access network (AN) and a core network. The clientdevice may include a network device (e.g., a residential gateway), amobile device (e.g., a user equipment), and/or the like that utilizes atransport protocol to carry messages via wireline access to the corenetwork. The AN may include one or more radio transmitters. The corenetwork may include an example architecture of a 5G next generation (NG)core network included in a 5G wireless telecommunications system, andmay include physical elements, virtual elements, or a combination ofphysical and virtual elements.

As further shown in FIG. 1A, and by reference number 105, the clientdevice may utilize PPPoE and PPP to register the client device with thecore network. In some implementations, the client device may utilizePPPoE and PPP as a transport protocol to carry messages via wirelineaccess to the core network, as described herein. In someimplementations, the client device may utilize PPPoE and PPP to registerthe client device with the core network using the call flow shown inFIG. 1B.

As shown in FIG. 1B, the client device may be associated with the AN,and an access gateway function (AGF), an access and mobility managementfunction (AMF), a session management function (SMF), and a user planefunction (UPF) of the core network. As further shown in FIG. 1B, theclient device may provide a registration initiation request (e.g., aPPPoE active discovery initiation (PADI) packet) to the AN, and the ANmay provide the registration initiation request (e.g., and an identifierof the client device) to the AGF. The AGF and the AMF may set up an N2interface provided between the AGF and the AMF. The AGF may provide anoffer response (e.g., a PPPoE active discovery offer (PADO) packet) tothe client device. The client device may provide a registration request(e.g., a PPPoE active discovery request (PADR) packet) to the AN, andthe AN may provide the registration request (e.g., and the identifier ofthe client device) to the AGF. The client device and the AGF mayestablish a PPP link control protocol (LCP) connection to exchangeinformation (e.g., a maximum receive unit (MRU), a randomly generatednumber (e.g., referred to as a magic number), authorization information,and/or the like).

As further shown in FIG. 1B, the client device may provide aregistration request (e.g., a PPP NAS registration request that includesnetwork slice selection assistance information (NSSAI)) to the AGF, andthe AGF may provide a next generation application protocol (NGAP)initial message (e.g., the registration request) to the AMF. Based onreceiving the initial message, the AMF may provide an NGAP downlink NAStransport identity request (e.g., that seeks an identity of the clientdevice) to the AGF, and the AGF may provide the identity request to theclient device via a PPP NAS downlink message. The client device mayprovide an identity response (e.g., identifying the client device), viaa PPP NAS uplink message, to the AGF, and the AGF may provide theidentity response to the AMF (e.g., via NGAP uplink NAS transport).Based on receiving the identity response, the AMF may provide an NGAPdownlink NAS transport authentication request (e.g., that seeksauthentication of the client device) to the AGF, and the AGF may providethe authentication request to the client device via a PPP NAS downlinkmessage. The client device may provide an authentication response (e.g.,authenticating the client device), via a PPP NAS uplink message, to theAGF, and the AGF may provide the identity response to the AMF (e.g., viaNGAP uplink NAS transport).

Based on receiving the authentication response, the AMF may provide anNGAP downlink NAS transport security mode command (e.g., to be executedby the client device) to the AGF, and the AGF may provide the securitymode command to the client device via a PPP NAS downlink message. Theclient device may execute the security mode command and provide asecurity mode complete response (e.g., indicating that the client deviceexecuted the security mode command), via a PPP NAS uplink message, tothe AGF, and the AGF may provide the security mode complete response tothe AMF (e.g., via NGAP uplink NAS transport). Based on receiving thesecurity mode complete response, the AMF may provide an NGAP downlinkNAS transport registration accept (e.g., to be accepted by the clientdevice) to the AGF, and the AGF may provide the registration accept tothe client device via a PPP NAS message. The client device may acceptthe registration and provide a registration complete response (e.g.,indicating that the client device executed the security mode command),via a PPP NAS uplink message, to the AGF. Based on receiving theregistration complete response, the AGF may provide registrationcomplete response to the AMF (e.g., via NGAP uplink NAS transport).

As shown in FIG. 1C, and by reference number 110, the client device mayutilize PPPoE and PPP to deregister the client device with the corenetwork and to release a PDU session (e.g., after registration of theclient device and based on ending a PDU session). In someimplementations, the client device may utilize PPPoE and PPP toderegister the client device with the core network using the call flowshown in FIG. 1D.

As shown in FIG. 1D, the client device may provide a deregistrationrequest to the AGF via a PPP NAS message, and the AGF may provide thederegistration request to the AMF (e.g., via NGAP uplink NAS transport).Based on receiving the deregistration request, the AMF may deregisterthe client device with the core network and may provide an NGAP downlinkNAS transport deregistration accept message to the AGF. The AGF mayprovide the deregistration accept message to the client device via a PPPNAS message. The AMF may also provide another NGAP downlink NAStransport deregistration request to the AGF, and the AGF may provide theother deregistration request to the client device via a PPP NAS message.The client device may accept the deregistration request and may provideanother deregistration accept message to the AGF via a PPP NAS message.The AGF may provide the other deregistration accept message to the AMF(e.g., via NGAP uplink NAS transport) and the client device may bederegistered with the core network.

As shown in FIG. 1E, and by reference number 115, the client device mayutilize PPPoE and PPP to configure a PDU session with the core network.In some implementations, the client device may utilize PPPoE and PPP toconfigure the PDU session with the core network using a top portion ofthe call flow shown in FIG. 1F. As further shown in FIG. 1E, and byreference number 120, the client device may utilize PPPoE and PPP tomodify the PDU session with the core network. In some implementations,the client device may utilize PPPoE and PPP to modify the PDU sessionwith the core network using a bottom portion of the call flow shown inFIG. 1F.

As shown at the top portion of FIG. 1F, the client device (e.g., inorder to establish and configure a PDU session) may provide a PDUsession establishment request to the AGF via a PPP NAS message, and theAGF may provide the PDU session establishment request to the AMF viaNGAP uplink NAS transport. Based on receiving the PDU sessionestablishment request, the AMF may provide a network slice managementfunction (NSMF) PDU session create request to the SMF, and the SMF mayprovide an N4 packet forwarding control protocol (PFCP) session createrequest to the UPF. The UPF may accept the N4 PFCP session createrequest and may provide an N4 PFCP session create response to the SMF.The SMF may provide an NSMF PDU session create response to the AMF, andthe AMF may provide a PDU session establishment accept to the AGF via aNGAP PDU session resource setup request. The AGF may provide the PDUsession establishment accept (e.g., and a data session identifier) tothe client device, and the client device may establish the PDU sessionwith the core network. Based on establishing the PDU session, the clientdevice may provide a PDU session establishment complete, via a PPP NASmessage, to the AGF, and the AGF may provide an NGAP PDU sessionresource setup response to the AMF. The AMF may provide an NSMF PDUsession modify request to the SMF, and the SMF may provide an N4 PFCPsession modify request to the UPF. The UPF may provide an N4 PFCPsession modify response to the SMF, and the SMF may provide an NSMFsession modify response to the AMF.

As shown at the bottom portion of FIG. 1F, the client device (e.g., inorder to modify a PDU session) may provide a PDU session modificationrequest, via a PPP NAS message, to the AGF. The AGF may provide the PDUsession modification request to the AMF via NGAP uplink NAS transport,and the AMF may provide an NSMF session modification request to the SMF.The SMF may provide an N4 PFCP session modify response to the UPF, andthe UPF may provide an N4 PFCP session modify response to the SMF. TheSMF may provide an NSMF session modify response to the AMF, and the AMFmay provide a PDU session modification command to the AGF via NGAPdownlink NAS transport. The AGF may provide the PDU session modificationcommand to the client device, via a PPP NAS downlink transport message,and the client device may execute the PDU session modification commandin order to modify the PDU session or may reject the modification. Theclient device may provide a PDU session modification complete/reject,via PPP NAS message, to the AGF, and the AGF may provide the PDU sessionmodification complete/reject to the AMF via NGAP uplink NAS transport.

As shown in FIG. 1G, and by reference number 125, the client device mayutilize PPPoE and PPP to release the PDU session with the core network.In some implementations, the client device may utilize PPPoE and PPP torelease the PDU session with the core network using the call flow shownin FIG. 1H.

As shown in FIG. 1H, the client device (e.g., in order to release thePDU session) may provide a PDU session release request to the AGF via aPPP NAS message, and the AGF may provide the PDU session release requestto the AMF via NGAP uplink NAS transport. Based on receiving the PDUsession release request, the AMF may provide an NSMF PDU session deleterequest to the SMF, and the SMF may provide an N4 PFCP session deleterequest to the UPF. The UPF may provide an N4 PFCP session deleteresponse (e.g., indicating that the PDU session will be deleted) to theSMF, and the SMF may provide a NSMF PDU session delete response to theAMF. Based on receiving the NSMF PDU session delete response, the AMFmay provide a PDU session release command to the AGF via NGAP downlinkNAS transport, and the AGF may provide the PDU session release commandto the client device via a PPP NAS message. The client device mayexecute the PDU session release command to release the PDU session ormay reject the command. The client device may then provide a PDU sessionrelease complete/reject, via a PPP NAS message, to the AGF, and the AGFmay provide the PDU session release complete/reject to the AMF via NGAPuplink NAS transport.

As shown in FIG. 1I, and by reference number 130, the client device mayutilize PPPoE and PPP to establish multiple PDU sessions with the corenetwork. In some implementations, the client device may utilize PPPoEand PPP to establish multiple PDU sessions with the core network usingthe call flows shown in FIGS. 1J and 1K.

As shown in FIG. 1J, the client device (e.g., in order to establish afirst PDU session and a second PDU session) may provide a registrationinitiation request (e.g., a PADI packet) and a session identifier (e.g.,0) to the AGF, and the AGF may provide an offer response (e.g., a PADO)packet to the client device. The AGF and the AMF may set up an N2interface provided between the AGF and the AMF. The client device mayprovide a registration request (e.g., a PADR packet) to the AGF, and theAGF may respond with a session confirmation (e.g., a PPPoE activediscovery session confirmation (PADS) packet) and a session identifier(e.g., X). The client device and the AMF may complete a registrationprocedure for the client device. The client device and the AGF maygenerate and transmit PPP keep alive messages in order to maintain thesession (e.g., session X).

As further shown in FIG. 1J, the client device (e.g., in order toestablish the first PDU session) may provide a PDU session establishmentrequest and a PDU session identifier (e.g., P1) to the AGF via a PPP NASmessage, and the AGF may provide the PDU session establishment requestto the AMF via NGAP uplink NAS transport. Based on receiving the PDUsession establishment request, the AMF may provide an NSMF PDU sessioncreate request to the SMF, and the SMF may provide an N4 PFCP sessioncreate request to the UPF. The UPF may accept the N4 PFCP session createrequest and may provide an N4 PFCP session create response to the SMF.The SMF may provide an NSMF PDU session create response to the AMF, andthe AMF may provide a PDU session establishment accept to the AGF via aPDU session resource setup request. The AGF may provide the PDU sessionestablishment accept (e.g., and a session identifier D1) to the clientdevice, and the client device may establish the first PDU session withthe core network. Based on establishing the first PDU session, theclient device may provide a PDU session establishment complete, via aPPP NAS message, to the AGF, and the AGF may provide a PDU sessionresource setup response to the AMF. The AMF may provide an NSMF PDUsession modify request to the SMF, and the SMF may provide an N4 PFCPsession modify request to the UPF. The UPF may provide an N4 PFCPsession modify response to the SMF, and the SMF may provide an NSMF PDUsession modify response to the AMF. The client device and the AGF maygenerate and transmit PPP keep alive messages in order to maintain thefirst PDU session (e.g., session D1). The AGF and the UPF may establisha first general packet radio service (GPRS) tunneling protocol (GTP)tunnel (e.g., T1) for the first PDU session.

As shown in FIG. 1K, the client device (e.g., in order to establish thesecond PDU session) may provide a PDU session establishment request anda PDU session identifier (e.g., P2) to the AGF via a PPP NAS message,and the AGF may provide the PDU session establishment request to the AMFvia NGAP uplink NAS transport. Based on receiving the PDU sessionestablishment request, the AMF may provide an NSMF PDU session createrequest to the SMF, and the SMF may provide an N4 PFCP session createrequest to the UPF. The UPF may accept the N4 PFCP session createrequest and may provide an N4 PFCP session create response to the SMF.The SMF may provide an NSMF PDU session create response to the AMF, andthe AMF may provide a PDU session establishment accept to the AGF via aPDU session resource setup request. The AGF may provide the PDU sessionestablishment accept (e.g., and a session identifier D2) to the clientdevice, and the client device may establish the second PDU session withthe core network. Based on establishing the second PDU session, theclient device may provide a PDU session establishment complete, via aPPP NAS message, to the AGF, and the AGF may provide a PDU sessionresource setup response to the AMF. The AMF may provide an NSMF PDUsession modify request to the SMF, and the SMF may provide an N4 PFCPsession modify request to the UPF. The UPF may provide an N4 PFCPsession modify response to the SMF, and the SMF may provide an NSMF PDUsession modify response to the AMF. The client device and the AGF maygenerate and transmit PPP keep alive messages in order to maintain thesecond PDU session (e.g., session D2). The AGF and the UPF may establisha GTP tunnel (e.g., T2) for the second PDU session.

FIG. 1L shows types of information utilized by the PPPoE and the PPP inimplementations described herein. As shown, the PPPoE may include bitsassociated with a PPP session stage, an offer (PADO), an initiation(PADI), a session grant (PADG), a session credit response (PADC), aquality (PADQ), a request (PADR), a session confirmation (PADS), aterminate (PADT), a message (PADM), and a network (PADN).

As further shown FIG. 1L, the PPP may include bits associated withInternet protocol version 4 (IPv4), a bridging PDU, multi-link, Internetprotocol version 6 (IPv6), 5G data, multi-protocol label switching(MPLS) unicast, MPLS multicast, a vendor-specific protocol (VSP), anInternet protocol control protocol, an IPv6 control protocol, avendor-specific network control protocol (VSNCP), 5G access stratum, alink control protocol, a password authentication protocol, avendor-specific authentication protocol (VSAP), a challenge handshakeauthentication protocol, and an extensible authentication protocol. Insome implementations, the bits associated with 5G data and 5G accessstratum may be newly provided in the PPP.

FIG. 1M shows information included in an Ethernet packet, a PPPoE packetof the Ethernet packet, and a PPP packet of the PPPoE packet that may beutilized in implementations described herein. For example, the Ethernetpacket encapsulation format may include a destination address field, asource address field, an Ethernet type field, a PPPoE packet field, anda checksum field. The PPPoE packet encapsulation format may include aversion field, a type field, a code field, a session identifier field, alength field, and a PPP packet field. The PPP packet encapsulationformat may include a flag field, an address field, a control field, aprotocol field, an information field, a frame check sequence (FCS)field, and another flag field.

FIG. 1N depicts a packet associated with 5G access stratum on PPPoE thatmay be utilized in implementations described herein. As shown, a firstportion of the packet may include a destination media access control(MAC) address field, a source MAC address field, an Ethernet type field,and a PPPoE field that points to a second portion of the packet. Thesecond portion of the packet may include a version field, a type field,a code field, a session identifier field, a length field, and a PPPfield that points to a third portion of the packet. The third portion ofthe packet may include a protocol field (e.g., that includes newlyprovided information “0x80XX”) and a payload field that points to afourth portion of the packet. The fourth portion of the packet mayinclude a 5G control field.

FIG. 1O shows types of 5G control NAS message formats for registrationand deregistration of the client device, as utilized by the PPPoE andthe PPP in implementations described herein. As shown in the left-handtable of FIG. 1O, the 5G NAS message format for registration may includea version field, a flags field, a message type=registration requestfield, an S-NSSAI[Octet 1] field, an S-NSSAI[Octet 2] field, anS-NSSAI[Octet 3] field, an S-NSSAI[Octet 4] field, a length of NASPDU[Octet 1] field, a length of NAS PDU[Octet 2] field, a number of typelength values (ATLVs) field, an ATLVs field, an NAS PDU[Octet 1] field,an NAS PDU[Octet 2] field, and an NAS PDU[Octet N] field. As shown inthe right-hand table of FIG. 1O, the 5G NAS message format forderegistration may include a version field, an attribute type lengthvalue (ATLV) flag field (e.g., that is unset when “0” and set when “1”),a flags field, a message type=registration accept/complete/reject,deregistration request/accept field, a length of NAS PDU[Octet 1] field,a length of NAS PDU[Octet 2] field, an NAS PDU[Octet 1] field, an NASPDU[Octet 2] field, and an NAS PDU[Octet N] field.

FIG. 1P shows types of 5G control NAS message formats for PDU sessionmanagement by the client device, as utilized by the PPPoE and the PPP inimplementations described herein. As shown in the left-hand table ofFIG. 1P, the 5G NAS message format for PDU session management mayinclude a version field, a flags field, a message type=PDU sessionestablishment request/reject/complete, PDU session modificationrequest/command/reject/complete, PDU session releaserequest/command/reject/complete field, a PDU session-ID field, aprocedure transaction ID (PTI) field, a length of NAS PDU[Octet 1]field, a length of NAS PDU[Octet 2] field, an NAS PDU[Octet 1] field, anNAS PDU[Octet 2] field, and an NAS PDU[Octet N] field. As shown in theright-hand table of FIG. 1P, the 5G NAS message format for PDU sessionestablishment accept may include a version field, a flags field, amessage type=PDU session establishment accept field, a PDU session-IDfield, a procedure transaction ID (PTI) field, a 5G datasession-ID[Octet 1] field, a 5G data session-ID[Octet 2] field, a lengthof NAS PDU[Octet 1] field, a length of NAS PDU[Octet 2] field, an NASPDU[Octet 1] field, an NAS PDU[Octet 2] field, and an NAS PDU[Octet N]field.

FIG. 1Q shows types of 5G control NAS message formats for uplink anddownlink transport, as utilized by the PPPoE and the PPP inimplementations described herein. As shown in the left-hand table ofFIG. 1Q, the 5G NAS message format for uplink and downlink transport mayinclude a version field, a flags field, a message type=uplink (UL)transport/downlink (DL) transport field, a PDU session-ID field, aprocedure transaction ID (PTI) field, a length of NAS PDU[Octet 1]field, a length of NAS PDU[Octet 2] field, an NAS PDU[Octet 1] field, anNAS PDU[Octet 2] field, and an NAS PDU[Octet N] field. As shown in theright-hand table of FIG. 1Q, the uplink transport may be utilized with aservice request, a configuration update complete, an authenticationresponse/failure, an identity response, a security mode complete/reject,a security protected 5G NAS message, a 5GMM status, a 5GSM status, and anotification response. The downlink transport may be utilized with aservice accept/reject, a configuration update command, an authenticationrequest/result/reject, an identity request, a security mode command, asecurity protected 5G NAS message, a 5GMM status, a 5GSM status, and anotification.

FIG. 1R depicts a packet associated with 5G data protocol on PPPoE thatmay be utilized in implementations described herein. As shown, a firstportion of the packet may include a destination MAC address field, asource MAC address field, an Ethernet type field, and a PPPoE field thatpoints to a second portion of the packet. The second portion of thepacket may include a version field, a type field, a code field, asession identifier field, a length field, and a PPP field that points toa third portion of the packet. The third portion of the packet mayinclude a protocol field (e.g., that includes newly provided information“0x00XX”) and a 5G data field that points to a fourth portion of thepacket. The fourth portion of the packet may include a version/flagsfield, a reflective quality of service (QoS) indicator (RQI)/QoS flowidentifier (QFI) field, a protocol field, and payload field.

FIG. 1S shows a message format for a 5G data payload, as utilized by thePPPoE and the PPP in implementations described herein. As shown, themessage format for the 5G data payload may include a version field, areflective QoS field, a flags field, a QFI field, a PPP protocol[Octet1] field, a PPP protocol[Octet 2] field, and a data field.

In this way, the client device utilizes a transport protocol to carrymessages via wireline access to a 5G core network, thereby improvingfunctioning of the 5G core network, the client device, and/or the like.For example, the client device may utilize PPPoE and PPP with a new setof protocol identifiers for control traffic and data traffic, and mayutilize the PPPoE and PPP to handle multiple PDU sessions and thusprovide different services to the multiple PDU sessions, as required.Furthermore, currently there does not exist a technique that utilizes atransport protocol to carry messages via wireline access to a 5G corenetwork in the manner described herein. Finally, the client deviceconserves computing resources (e.g., processing resources, memoryresources, communication resources, and/or the like), networkingresources, and/or the like that would otherwise be wasted in performingdeep packet inspection, determining 5G capability of a client device,modifying an access network, handling network attacks, and/or the like.

Furthermore, implementations described herein may provide a lightweightprotocol since no other protocol is provided overhead to carry packetseither for control, and may enable the control plane to allocate sessionidentifiers for the data plane, which keeps the control plane in controlof data sessions and prevents collisions and attacks. Implementationsdescribed herein may support 5G stringent scales and latencyrequirements, and may provide simple packet formats that can processedby data plane hardware and software.

As indicated above, FIGS. 1A-1S are provided merely as examples. Otherexamples may differ from what is described with regard to FIGS. 1A-1S.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2,example environment 200 may include client device 205, AN 210, corenetwork 215, and a data network 275. Devices and/or networks of exampleenvironment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

Client device 205 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information, such asinformation described herein. For example, client device 205 may includea residential gateway, a user equipment, a network device (e.g., a labelswitching router (LSR), a label edge router (LER), an ingress router, anegress router, a provider router, a virtual router, a gateway, a switch,a firewall, a hub, a bridge, a reverse proxy, a proxy server, a cloudserver, a data center server, a load balancer, and/or the like), or asimilar type of device. In some implementations, client device 205 mayreceive network traffic from and/or may provide network traffic to corenetwork 215, via AN 210.

AN 210 may include one or more nodes that are associated with a wirelineconnection to core network 215. AN 210 may include a central unit (CU)that includes a next generation (NG) interface connecting the CU to acore unit (e. g., a next gen core (NGC) unit), which may be a node ofcore network 215. AN 210 may transfer traffic between client device 205and core network 215. In some implementations, AN 210 may performscheduling and/or resource management for client device 205 covered byAN 210. In some implementations, AN 210 may be controlled or coordinatedby a network controller, which may perform load balancing, network-levelconfiguration, and/or the like. The network controller may communicatewith AN 210 via a wireless or wireline backhaul. In someimplementations, AN 210 may include a network controller, aself-organizing network (SON) module or component, or a similar moduleor component. In other words, AN 210 may perform network control,scheduling, and/or network management functions (e.g., for uplink,downlink, and/or sidelink communications of client device 205 covered byAN 210).

In some implementations, core network 215 may include an examplefunctional architecture in which systems and/or methods described hereinmay be implemented. For example, core network 215 may include an examplearchitecture of a fifth generation (5G) next generation (NG) corenetwork included in a 5G wireless telecommunications system. While theexample architecture of core network 215 shown in FIG. 2 may be anexample of a service-based architecture, in some implementations, corenetwork 215 may be implemented as a reference-point architecture.

As shown in FIG. 2, core network 215 may include a number of functionalelements. The functional elements may include, for example, a networkslice selection function (NSSF) 220, a network exposure function (NEF)225, an authentication server function (AUSF) 230, a unified datamanagement (UDM) component 235, a policy control function (PCF) 240, anapplication function (AF) 245, an access and mobility managementfunction (AMF) 250, an access gateway function (AGF) 255, a sessionmanagement function (SMF) 260, a user plane function (UPF) 265, and/orthe like. These functional elements may be communicatively connected viaa message bus 270. Each of the functional elements shown in FIG. 2 isimplemented on one or more devices associated with a wirelesstelecommunications system. In some implementations, one or more of thefunctional elements may be implemented on physical devices, such as anaccess point, a base station, a gateway, and/or the like. In someimplementations, one or more of the functional elements may beimplemented on a computing device of a cloud computing environment.

NSSF 220 includes one or more devices that select network sliceinstances for client device 205. By providing network slicing, NSSF 220allows an operator to deploy multiple substantially independentend-to-end networks potentially with the same infrastructure. In someimplementations, each slice may be customized for different services.

NEF 225 includes one or more devices that support exposure ofcapabilities and/or events in the wireless telecommunications system tohelp other entities in the wireless telecommunications system discovernetwork services.

AUSF 230 includes one or more devices that act as an authenticationserver and support the process of authenticating client device 205 inthe wireless telecommunications system.

UDM 235 includes one or more devices that store user data and profilesin the wireless telecommunications system. UDM 235 may be used for fixedaccess, mobile access, and/or the like, in core network 215.

PCF 240 includes one or more devices that provide a policy frameworkthat incorporates network slicing, roaming, packet processing, mobilitymanagement, and/or the like.

AF 245 includes one or more devices that support application influenceon traffic routing, access to NEF 225, policy control, and/or the like.

AMF 250 includes one or more devices that act as a termination point fornon-access stratum (NAS) signaling, mobility management, and/or thelike.

AGF 255 includes one or more devices, between a wireline accessinfrastructure (e.g., AN 210) and wireless core network 215, thatsupport residential gateways (e.g., client device 205) that include 5GNAS signaling and residential gateways that are purely wireline.

SMF 260 includes one or more devices that support the establishment,modification, and release of communications sessions in the wirelesstelecommunications system. For example, SMF 260 may configure trafficsteering policies at UPF 265, enforce user equipment IP addressallocation and policies, and/or the like.

UPF 265 includes one or more devices that serve as an anchor point forintraRAT and/or interRAT mobility. UPF 265 may apply rules to packets,such as rules pertaining to packet routing, traffic reporting, handlinguser plane QoS, and/or the like.

Message bus 270 represents a communication structure for communicationamong the functional elements. In other words, message bus 270 maypermit communication between two or more functional elements.

Data network 275 includes one or more wired and/or wireless datanetworks. For example, data network 275 may include an IP MultimediaSubsystem (IMS), a public land mobile network (PLMN), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a private network such as a corporate intranet, an ad hocnetwork, the Internet, a fiber optic-based network, a cloud computingnetwork, a third party services network, an operator services network,and/or the like, and/or a combination of these or other types ofnetworks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) of exampleenvironment 200 may perform one or more functions described as beingperformed by another set of devices of example environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to client device 205, NSSF 220, NEF 225, AUSF 230, UDM235, PCF 240, AF 245, AMF 250, AGF 255, SMF 260, and/or UPF 265. In someimplementations, client device 205, NSSF 220, NEF 225, AUSF 230, UDM235, PCF 240, AF 245, AMF 250, AGF 255, SMF 260, and/or UPF 265 mayinclude one or more devices 300 and/or one or more components of device300. As shown in FIG. 3, device 300 may include one or more inputcomponents 305-1 through 305-A (A≥1) (hereinafter referred tocollectively as input components 305, and individually as inputcomponent 305), a switching component 310, one or more output components315-1 through 315-B (B≥1) (hereinafter referred to collectively asoutput components 315, and individually as output component 315), and acontroller 320.

Input components 305 may be points of attachment for physical links andmay be points of entry for incoming traffic, such as packets. Inputcomponent 305 may process incoming traffic, such as by performing datalink layer encapsulation or decapsulation. In some implementations,input component 305 may send and/or receive packets. In someimplementations, input component 305 may include an input line card thatincludes one or more packet processing components (e.g., in the form ofintegrated circuits), such as one or more interface cards (IFCs), packetforwarding components, line card controller components, input ports,processors, memories, and/or input queues. In some implementations,device 300 may include one or more input components 305.

Switching component 310 may interconnect input components 305 withoutput components 315. In some implementations, switching component 310may be implemented via one or more crossbars, via busses, and/or withshared memories. The shared memories may act as temporary buffers tostore packets from input components 305 before the packets areeventually scheduled for delivery to output components 315. In someimplementations, switching component 310 may enable input components305, output components 315, and/or controller 320 to communicate.

Output component 315 may store packets and may schedule packets fortransmission on output physical links. Output component 315 may supportdata link layer encapsulation or decapsulation, and/or a variety ofhigher-level protocols. In some implementations, output component 315may send packets and/or receive packets. In some implementations, outputcomponent 315 may include an output line card that includes one or morepacket processing components (e.g., in the form of integrated circuits),such as one or more IFCs, packet forwarding components, line cardcontroller components, output ports, processors, memories, and/or outputqueues. In some implementations, device 300 may include one or moreoutput components 315. In some implementations, input component 305 andoutput component 315 may be implemented by the same set of components(e.g., and input/output component may be a combination of inputcomponent 305 and output component 315).

Controller 320 includes a processor in the form of a central processingunit (CPU), a graphics processing unit (GPU), an accelerated processingunit (APU), a microprocessor, a microcontroller, a digital signalprocessor (DSP), a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), and/or another type ofprocessor or processing component. The processor is implemented inhardware, firmware, and/or a combination of software and hardware. Insome implementations, controller 320 may include one or more processorsthat can be programmed to perform a function.

In some implementations, controller 320 may include a random-accessmemory (RAM), a read only memory (ROM), and/or another type of dynamicor static storage device (e.g., a flash memory, a magnetic memory, anoptical memory, and/or the like) that stores information and/orinstructions for use by controller 320.

In some implementations, controller 320 may communicate with otherdevices, networks, and/or systems connected to device 300 to exchangeinformation regarding network topology. Controller 320 may createrouting tables based on the network topology information, createforwarding tables based on the routing tables, and forward theforwarding tables to input components 305 and/or output components 315.Input components 305 and/or output components 315 may use the forwardingtables to perform route lookups for incoming and/or outgoing packets. Insome cases, controller 320 may create a session table based oninformation determined while initializing a link fault detection sessionand may forward the session table to input components 305 and/or outputcomponents 315.

Controller 320 may perform one or more processes described herein.Controller 320 may perform these processes in response to executingsoftware instructions stored by a non-transitory computer-readablemedium. A computer-readable medium is defined herein as a non-transitorymemory device. A memory device includes memory space within a singlephysical storage device or memory space spread across multiple physicalstorage devices.

Software instructions may be read into a memory and/or storage componentassociated with controller 320 from another computer-readable medium orfrom another device via a communication interface. When executed,software instructions stored in a memory and/or storage componentassociated with controller 320 may cause controller 320 to perform oneor more processes described herein. Additionally, or alternatively,hardwired circuitry may be used in place of or in combination withsoftware instructions to perform one or more processes described herein.Thus, implementations described herein are not limited to any specificcombination of hardware circuitry and software.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a diagram of example components of a device 400. Device 400may correspond to client device 205, NSSF 220, NEF 225, AUSF 230, UDM235, PCF 240, AF 245, AMF 250, AGF 255, SMF 260, and/or UPF 265. In someimplementations, client device 205, NSSF 220, NEF 225, AUSF 230, UDM235, PCF 240, AF 245, AMF 250, AGF 255, SMF 260, and/or UPF 265 mayinclude one or more devices 400 and/or one or more components of device400. As shown in FIG. 4, device 400 may include a bus 410, a processor420, a memory 430, a storage component 440, an input component 450, anoutput component 460, and a communication interface 470.

Bus 410 includes a component that permits communication among thecomponents of device 400. Processor 420 is implemented in hardware,firmware, or a combination of hardware and software. Processor 420 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 420includes one or more processors capable of being programmed to perform afunction. Memory 430 includes a random-access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 420.

Storage component 440 stores information and/or software related to theoperation and use of device 400. For example, storage component 440 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid-state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 450 includes a component that permits device 400 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 450 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 460 includes a component that providesoutput information from device 400 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 470 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 400 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 470 may permit device 400to receive information from another device and/or provide information toanother device. For example, communication interface 470 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface,and/or the like.

Device 400 may perform one or more processes described herein. Device400 may perform these processes based on processor 420 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 430 and/or storage component 440.

Software instructions may be read into memory 430 and/or storagecomponent 440 from another computer-readable medium or from anotherdevice via communication interface 470. When executed, softwareinstructions stored in memory 430 and/or storage component 440 may causeprocessor 420 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 4 are provided asan example. In practice, device 400 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 4. Additionally, or alternatively, aset of components (e.g., one or more components) of device 400 mayperform one or more functions described as being performed by anotherset of components of device 400.

FIG. 5 is a flow chart of an example process 500 for utilizing atransport protocol for 5G client devices to carry messages on wirelineaccess. In some implementations, one or more process blocks of FIG. 5may be performed by a device (e.g., client device 205). In someimplementations, one or more process blocks of FIG. 5 may be performedby another device or a group of devices separate from or including thedevice, such as one or more devices of a core network (e.g., corenetwork 215).

As shown in FIG. 5, process 500 may include utilizing a point-to-pointprotocol over Ethernet (PPPoE) and a point-to-point protocol (PPP) toregister the device with a core network (block 510). For example, thedevice (e.g., using input component 305, switching component 310, outputcomponent 315, controller 320, processor 420, communication interface470, and/or the like) may utilize a PPPoE and a PPP to register thedevice with a core network, as described above.

As further shown in FIG. 5, process 500 may include establishing a firstpacket data unit (PDU) session with the core network based on the PPPoEand the PPP (block 520). For example, the device (e.g., using inputcomponent 305, switching component 310, output component 315, controller320, processor 420, memory 430, communication interface 470, and/or thelike) may establish a first PDU session with the core network based onthe PPPoE and the PPP, as described above.

As further shown in FIG. 5, process 500 may include configuring thefirst PDU session with the core network based on the PPPoE and the PPP,wherein the first PDU session is configured to provide a first service(block 530). For example, the device (e.g., using input component 305,switching component 310, output component 315, controller 320, processor420, storage component 440, communication interface 470, and/or thelike) may configure the first PDU session with the core network based onthe PPPoE and the PPP, as described above. In some implementations, thefirst PDU session may be configured to provide a first service.

As further shown in FIG. 5, process 500 may include generating firstkeep alive messages to maintain the first PDU session with the corenetwork (block 540). For example, the device (e.g., using switchingcomponent 310, output component 315, controller 320, processor 420,communication interface 470, and/or the like) may generate first keepalive messages to maintain the first PDU session with the core network,as described above.

As further shown in FIG. 5, process 500 may include establishing asecond PDU session with the core network based on the PPPoE and the PPP(block 550). For example, the device (e.g., using input component 305,switching component 310, output component 315, controller 320, processor420, memory 430, communication interface 470, and/or the like) mayestablish a second PDU session with the core network based on the PPPoEand the PPP, as described above.

As further shown in FIG. 5, process 500 may include configuring thesecond PDU session with the core network based on the PPPoE and the PPP,wherein the second PDU session is configured to provide a second servicethat is different than the first service (block 560). For example, thedevice (e.g., using input component 305, switching component 310, outputcomponent 315, controller 320, processor 420, storage component 440,communication interface 470, and/or the like) may configure the secondPDU session with the core network based on the PPPoE and the PPP, asdescribed above. In some implementations, the second PDU session isconfigured to provide a second service that is different than the firstservice.

As further shown in FIG. 5, process 500 may include generating secondkeep alive messages to maintain the second PDU session with the corenetwork (block 570). For example, the device (e.g., using switchingcomponent 310, output component 315, controller 320, processor 420,memory 430, communication interface 470, and/or the like) may generatesecond keep alive messages to maintain the second PDU session with thecore network, as described above.

Process 500 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, process 500 may include modifying one of thefirst PDU session or the second PDU session based on the PPPoE and thePPP.

In a second implementation, alone or in combination with the firstimplementation, modifying one of the first PDU session or the second PDUsession may include providing a PPP NAS PDU session modification requestto the core network; receiving a PPP NAS PDU session modificationcommand from the core network based on providing the PPP NAS PDU sessionmodification request; modifying the first PDU session or the second PDUsession based on executing the PPP NAS PDU session modification command;and providing a PPP NAS PDU session modification complete indication tothe core network based on executing the PPP NAS PDU session modificationcommand.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, process 500 may include releasingone of the first PDU session or the second PDU session based on thePPPoE and the PPP.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, process 500 may includereleasing the first PDU session and the second PDU session based on thePPPoE and the PPP, and after a period of time; and deregistering thedevice with the core network based on releasing the first PDU sessionand the second PDU session.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, releasing the first PDUsession and the second PDU session may include providing a PPP NAS firstPDU session release request to the core network; receiving a PPP NASfirst PDU session release command from the core network based onproviding the PPP NAS first PDU session release request; releasing thefirst PDU session based on executing the PPP NAS first PDU sessionrelease command; providing a PPP NAS first PDU session release completeindication to the core network based on executing the PPP NAS first PDUsession release command; providing a PPP NAS second PDU session releaserequest to the core network; receiving a PPP NAS second PDU sessionrelease command from the core network based on providing the PPP NASsecond PDU session release request; releasing the second PDU sessionbased on executing the PPP NAS second PDU session release command; andproviding a PPP NAS second PDU session release complete indication tothe core network based on executing the PPP NAS second PDU sessionrelease command.

In a sixth implementation, alone or in combination with one or more ofthe first through fifth implementations, deregistering the device withthe core network may include providing a PPP NAS deregistration requestto the core network; receiving a PPP NAS deregistration accept messagefrom the core network based on providing the PPP NAS deregistrationrequest; receiving another PPP NAS deregistration request from the corenetwork; and providing another PPP NAS deregistration accept message tothe core network based on receiving the other PPP NAS deregistrationrequest.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a flow chart of an example process 600 for utilizing atransport protocol for 5G client devices to carry messages on wirelineaccess. In some implementations, one or more process blocks of FIG. 6may be performed by a device (e.g., client device 205). In someimplementations, one or more process blocks of FIG. 6 may be performedby another device or a group of devices separate from or including thedevice, such as one or more devices of a core network (e.g., corenetwork 215).

As shown in FIG. 6, process 600 may include utilizing a PPPoE and a PPPto register the device with a core network (block 610). For example, thedevice (e.g., using input component 305, switching component 310, outputcomponent 315, controller 320, processor 420, memory 430, communicationinterface 470, and/or the like) may utilize a PPPoE and a PPP toregister the device with a core network, as described above.

As further shown in FIG. 6, process 600 may include establishing a firstPDU session with the core network based on the PPPoE and the PPP (block620). For example, the device (e.g., using input component 305,switching component 310, output component 315, controller 320, processor420, storage component 440, communication interface 470, and/or thelike) may establish a first PDU session with the core network based onthe PPPoE and the PPP, as described above.

As further shown in FIG. 6, process 600 may include configuring thefirst PDU session with the core network based on the PPPoE and the PPP,wherein the first PDU session is configured to provide a first service(block 630). For example, the device (e.g., using input component 305,switching component 310, output component 315, controller 320, processor420, memory 430, communication interface 470, and/or the like) mayconfigure the first PDU session with the core network based on the PPPoEand the PPP, as described above. In some implementations, the first PDUsession is configured to provide a first service.

As further shown in FIG. 6, process 600 may include establishing asecond PDU session with the core network based on the PPPoE and the PPP(block 640). For example, the device (e.g., using input component 305,switching component 310, output component 315, controller 320, processor420, storage component 440, communication interface 470, and/or thelike) may establish a second PDU session with the core network based onthe PPPoE and the PPP, as described above.

As further shown in FIG. 6, process 600 may include configuring thesecond PDU session with the core network based on the PPPoE and the PPP,wherein the second PDU session is configured to provide a second servicethat is different than the first service (block 650). For example, thedevice (e.g., using input component 305, switching component 310, outputcomponent 315, controller 320, processor 420, memory 430, storagecomponent 440, communication interface 470, and/or the like) mayconfigure the second PDU session with the core network based on thePPPoE and the PPP, as described above. In some implementations, thesecond PDU session is configured to provide a second service that isdifferent than the first service.

Process 600 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, the device may include a residential gatewayor a user equipment.

In a second implementation, alone or in combination with the firstimplementation, utilizing the PPPoE and the PPP to register the devicewith the core network may include providing a PPP NAS registrationrequest to the core network; receiving a PPP NAS downlink transportidentity request from the core network based on providing the PPP NASregistration request; providing a PPP NAS uplink transport identityresponse to the core network based on the PPP NAS downlink transportidentity request, wherein the PPP NAS uplink transport identity responseincludes an identity of the device; receiving a PPP NAS downlinktransport authentication request from the core network based onproviding the PPP NAS uplink transport identity response; providing aPPP NAS uplink transport authentication response to the core networkbased on the PPP NAS downlink transport authentication request, whereinthe PPP NAS uplink transport authentication response includesauthentication credentials of the device; receiving a PPP NAS downlinktransport security mode command from the core network based on providingthe PPP NAS uplink transport authentication response; providing, to thecore network, a PPP NAS uplink transport indication of execution of thesecurity mode command based on executing the PPP NAS downlink transportsecurity mode command; and receiving, from the core network, anindication that the device is registered with the core network based onproviding the PPP NAS uplink transport indication of execution of thesecurity mode command.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, establishing the first PDU sessionwith the core network may include providing a PPP NAS first PDU sessionestablishment request to the core network; receiving a PPP NAS first PDUsession accept message from the core network based on providing the PPPNAS first PDU session establishment request, wherein the PPP NAS firstPDU session accept message includes a first session identifier for thefirst PDU session; establishing the first PDU session with the corenetwork based on receiving the PPP NAS first PDU session accept messagefrom the core network; and providing a PPP NAS first PDU sessionestablishment complete indication to the core network based onestablishing the first PDU session with the core network.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, establishing the second PDUsession with the core network may include providing a PPP NAS second PDUsession establishment request to the core network; receiving a PPP NASsecond PDU session accept message from the core network based onproviding the PPP NAS second PDU session establishment request, whereinthe PPP NAS second PDU session accept message includes a second sessionidentifier for the second PDU session; establishing the second PDUsession with the core network based on receiving the PPP NAS second PDUsession accept message from the core network; and providing a PPP NASsecond PDU session establishment complete indication to the core networkbased on establishing the second PDU session with the core network.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, process 600 may includecausing a first tunnel to be created in the core network based onestablishing the first PDU session with the core network; and causing asecond tunnel to be created in the core network based on establishingthe second PDU session with the core network.

In a sixth implementation, alone or in combination with one or more ofthe first through fifth implementations, the core network may include afifth generation core network.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

FIG. 7 is a flow chart of an example process 700 for utilizing atransport protocol for 5G client devices to carry messages on wirelineaccess. In some implementations, one or more process blocks of FIG. 7may be performed by a device (e.g., client device 205). In someimplementations, one or more process blocks of FIG. 7 may be performedby another device or a group of devices separate from or including thedevice, such as one or more devices of a core network (e.g., corenetwork 215).

As shown in FIG. 7, process 700 may include utilizing a PPPoE and a PPPto register the device with a core network (block 710). For example, thedevice (e.g., using input component 305, switching component 310, outputcomponent 315, controller 320, processor 420, memory 430, communicationinterface 470, and/or the like) may utilize a PPPoE and a PPP toregister the device with a core network, as described above.

As further shown in FIG. 7, process 700 may include establishing a firstPDU session with the core network based on the PPPoE and the PPP (block720). For example, the device (e.g., using input component 305,switching component 310, output component 315, controller 320, processor420, storage component 440, communication interface 470, and/or thelike) may establish a first PDU session with the core network based onthe PPPoE and the PPP, as described above.

As further shown in FIG. 7, process 700 may include configuring thefirst PDU session with the core network based on the PPPoE and the PPP,wherein the first PDU session is configured to provide a first service(block 730). For example, the device (e.g., using input component 305,switching component 310, output component 315, controller 320, processor420, memory 430, storage component 440, communication interface 470,and/or the like) may configure the first PDU session with the corenetwork based on the PPPoE and the PPP, as described above. In someimplementations, the first PDU session is configured to provide a firstservice.

As further shown in FIG. 7, process 700 may include transmitting firstkeep alive messages to maintain the first PDU session with the corenetwork (block 740). For example, the device (e.g., using switchingcomponent 310, output component 315, controller 320, processor 420,memory 430, communication interface 470, and/or the like) may transmitfirst keep alive messages to maintain the first PDU session with thecore network, as described above.

Process 700 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, process 700 may include establishing a secondPDU session with the core network based on the PPPoE and the PPP;configuring the second PDU session with the core network based on thePPPoE and the PPP, wherein the second PDU session may be configured toprovide a second service that is different than the first service; andtransmitting second keep alive messages to maintain the second PDUsession with the core network.

In a second implementation, alone or in combination with the firstimplementation, process 700 may include modifying the first PDU sessionbased on the PPPoE and the PPP.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, process 700 may include releasingthe first PDU session based on the PPPoE and the PPP and after a periodof time, and deregistering the device with the core network based onreleasing the first PDU session.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, utilizing the PPPoE and the PPPto register the device with the core network may include providing a PPPNAS registration request to the core network; receiving a PPP NASdownlink transport identity request from the core network based onproviding the PPP NAS registration request; providing a PPP NAS uplinktransport identity response to the core network based on the PPP NASdownlink transport identity request, wherein the PPP NAS uplinktransport identity response includes an identity of the device;receiving a PPP NAS downlink transport authentication request from thecore network based on providing the PPP NAS uplink transport identityresponse; providing a PPP NAS uplink transport authentication responseto the core network based on the PPP NAS downlink transportauthentication request, wherein the PPP NAS uplink transportauthentication response includes authentication credentials of thedevice; receiving a PPP NAS downlink transport security mode commandfrom the core network based on providing the PPP NAS uplink transportauthentication response; providing, to the core network, a PPP NASuplink transport indication of execution of the security mode commandbased on executing the PPP NAS downlink transport security mode command;and receiving, from the core network, an indication that the device isregistered with the core network based on providing the PPP NAS uplinktransport indication of execution of the security mode command.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, establishing the first PDUsession with the core network may include providing a PPP NAS first PDUsession establishment request to the core network; receiving a PPP NASfirst PDU session accept message from the core network based onproviding the PPP NAS first PDU session establishment request, whereinthe PPP NAS first PDU session accept message includes a first sessionidentifier for the first PDU session; establishing the first PDU sessionwith the core network based on receiving the PPP NAS first PDU sessionaccept message from the core network; and providing a PPP NAS first PDUsession establishment complete indication to the core network based onestablishing the first PDU session with the core network.

Although FIG. 7 shows example blocks of process 700, in someimplementations, process 700 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 7. Additionally, or alternatively, two or more of theblocks of process 700 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

It will be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, or a combinationof hardware and software. The actual specialized control hardware orsoftware code used to implement these systems and/or methods is notlimiting of the implementations. Thus, the operation and behavior of thesystems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwaremay be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, a combination of related and unrelated items,etc.), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

What is claimed is:
 1. A method, comprising: utilizing, by a device, apoint-to-point protocol over Ethernet (PPPoE) and a point-to-pointprotocol (PPP) to register the device with a core network; establishing,by the device, a first packet data unit (PDU) session with the corenetwork based on the PPPoE and the PPP; configuring, by the device, thefirst PDU session with the core network based on the PPPoE and the PPP,wherein the first PDU session is configured to provide a first service;generating, by the device, first keep alive messages to maintain thefirst PDU session with the core network; establishing, by the device, asecond PDU session with the core network based on the PPPoE and the PPP;configuring, by the device, the second PDU session with the core networkbased on the PPPoE and the PPP, wherein the second PDU session isconfigured to provide a second service that is different than the firstservice; and generating, by the device, second keep alive messages tomaintain the second PDU session with the core network.
 2. The method ofclaim 1, further comprising: modifying one of the first PDU session orthe second PDU session based on the PPPoE and the PPP.
 3. The method ofclaim 2, wherein modifying one of the first PDU session or the secondPDU session comprises: providing a PPP non-access stratum (NAS) PDUsession modification request to the core network; receiving a PPP NASPDU session modification command from the core network based onproviding the PPP NAS PDU session modification request; modifying thefirst PDU session or the second PDU session based on executing the PPPNAS PDU session modification command; and providing a PPP NAS PDUsession modification complete indication to the core network based onexecuting the PPP NAS PDU session modification command.
 4. The method ofclaim 1, further comprising: releasing one of the first PDU session orthe second PDU session based on the PPPoE and the PPP.
 5. The method ofclaim 1, further comprising: releasing the first PDU session and thesecond PDU session based on the PPPoE and the PPP and after a period oftime; and deregistering the device with the core network based onreleasing the first PDU session and the second PDU session.
 6. Themethod of claim 5, wherein releasing the first PDU session and thesecond PDU session comprises: providing a PPP non-access stratum (NAS)first PDU session release request to the core network; receiving a PPPNAS first PDU session release command from the core network based onproviding the PPP NAS first PDU session release request; releasing thefirst PDU session based on executing the PPP NAS first PDU sessionrelease command; providing a PPP NAS first PDU session release completeindication to the core network based on executing the PPP NAS first PDUsession release command; providing a PPP NAS second PDU session releaserequest to the core network; receiving a PPP NAS second PDU sessionrelease command from the core network based on providing the PPP NASsecond PDU session release request; releasing the second PDU sessionbased on executing the PPP NAS second PDU session release command; andproviding a PPP NAS second PDU session release complete indication tothe core network based on executing the PPP NAS second PDU sessionrelease command.
 7. The method of claim 5, wherein deregistering thedevice with the core network comprises: providing a PPP non-accessstratum (NAS) deregistration request to the core network; receiving aPPP NAS deregistration accept message from the core network based onproviding the PPP NAS deregistration request; receiving another PPP NASderegistration request from the core network; and providing another PPPNAS deregistration accept message to the core network based on receivingthe other PPP NAS deregistration request.
 8. A device, comprising: oneor more memories; and one or more processors to: utilize apoint-to-point protocol over Ethernet (PPPoE) and a point-to-pointprotocol (PPP) to register the device with a core network; establish afirst packet data unit (PDU) session with the core network based on thePPPoE and the PPP; configure the first PDU session with the core networkbased on the PPPoE and the PPP, wherein the first PDU session isconfigured to provide a first service; establish a second PDU sessionwith the core network based on the PPPoE and the PPP; and configure thesecond PDU session with the core network based on the PPPoE and the PPP,wherein the second PDU session is configured to provide a second servicethat is different than the first service.
 9. The device of claim 8,wherein the device includes one of: a residential gateway, or a userequipment.
 10. The device of claim 8, wherein the one or moreprocessors, when utilizing the PPPoE and the PPP to register the devicewith the core network, are to: provide a PPP non-access stratum (NAS)registration request to the core network; receive a PPP NAS downlinktransport identity request from the core network based on providing thePPP NAS registration request; provide a PPP NAS uplink transportidentity response to the core network based on the PPP NAS downlinktransport identity request, wherein the PPP NAS uplink transportidentity response includes an identity of the device; receive a PPP NASdownlink transport authentication request from the core network based onproviding the PPP NAS uplink transport identity response; provide a PPPNAS uplink transport authentication response to the core network basedon the PPP NAS downlink transport authentication request, wherein thePPP NAS uplink transport authentication response includes authenticationcredentials of the device; receive a PPP NAS downlink transport securitymode command from the core network based on providing the PPP NAS uplinktransport authentication response; provide, to the core network, a PPPNAS uplink transport indication of execution of the security modecommand based on executing the PPP NAS downlink transport security modecommand; and receive, from the core network, an indication that thedevice is registered with the core network based on providing the PPPNAS uplink transport indication of execution of the security modecommand.
 11. The device of claim 8, wherein the one or more processors,when establishing the first PDU session with the core network, are to:provide a PPP non-access stratum (NAS) first PDU session establishmentrequest to the core network; receive a PPP NAS first PDU session acceptmessage from the core network based on providing the PPP NAS first PDUsession establishment request, wherein the PPP NAS first PDU sessionaccept message includes a first session identifier for the first PDUsession; establish the first PDU session with the core network based onreceiving the PPP NAS first PDU session accept message from the corenetwork; and provide a PPP NAS first PDU session establishment completeindication to the core network based on establishing the first PDUsession with the core network.
 12. The device of claim 8, wherein theone or more processors, when establishing the second PDU session withthe core network, are to: provide a PPP non-access stratum (NAS) secondPDU session establishment request to the core network; receive a PPP NASsecond PDU session accept message from the core network based onproviding the PPP NAS second PDU session establishment request, whereinthe PPP NAS second PDU session accept message includes a second sessionidentifier for the second PDU session; establish the second PDU sessionwith the core network based on receiving the PPP NAS second PDU sessionaccept message from the core network; and provide a PPP NAS second PDUsession establishment complete indication to the core network based onestablishing the second PDU session with the core network.
 13. Thedevice of claim 8, wherein the one or more processors are further to:cause a first tunnel to be created in the core network based onestablishing the first PDU session with the core network; and cause asecond tunnel to be created in the core network based on establishingthe second PDU session with the core network.
 14. The device of claim 8,wherein the core network includes a fifth generation core network.
 15. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors of a device, cause the one or more processors to:utilize a point-to-point protocol over Ethernet (PPPoE) and apoint-to-point protocol (PPP) to register the device with a corenetwork; establish a first packet data unit (PDU) session with the corenetwork based on the PPPoE and the PPP; configure the first PDU sessionwith the core network based on the PPPoE and the PPP, wherein the firstPDU session is configured to provide a first service; and transmit firstkeep alive messages to maintain the first PDU session with the corenetwork.
 16. The non-transitory computer-readable medium of claim 15,wherein the instructions further comprise: one or more instructionsthat, when executed by the one or more processors, cause the one or moreprocessors to: establish a second PDU session with the core networkbased on the PPPoE and the PPP; configure the second PDU session withthe core network based on the PPPoE and the PPP, wherein the second PDUsession is configured to provide a second service that is different thanthe first service; and transmit second keep alive messages to maintainthe second PDU session with the core network.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the instructions furthercomprise: one or more instructions that, when executed by the one ormore processors, cause the one or more processors to: modify the firstPDU session based on the PPPoE and the PPP.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the instructions furthercomprise: one or more instructions that, when executed by the one ormore processors, cause the one or more processors to: release the firstPDU session based on the PPPoE and the PPP and after a period of time;and deregister the device with the core network based on releasing thefirst PDU session.
 19. The non-transitory computer-readable medium ofclaim 15, wherein the one or more instructions, that cause the one ormore processors to utilize the PPPoE and the PPP to register the devicewith the core network, cause the one or more processors to: provide aPPP non-access stratum (NAS) registration request to the core network;receive a PPP NAS downlink transport identity request from the corenetwork based on providing the PPP NAS registration request; provide aPPP NAS uplink transport identity response to the core network based onthe PPP NAS downlink transport identity request, wherein the PPP NASuplink transport identity response includes an identity of the device;receive a PPP NAS downlink transport authentication request from thecore network based on providing the PPP NAS uplink transport identityresponse; provide a PPP NAS uplink transport authentication response tothe core network based on the PPP NAS downlink transport authenticationrequest, wherein the PPP NAS uplink transport authentication responseincludes authentication credentials of the device; receive a PPP NASdownlink transport security mode command from the core network based onproviding the PPP NAS uplink transport authentication response; provide,to the core network, a PPP NAS uplink transport indication of executionof the security mode command based on executing the PPP NAS downlinktransport security mode command; and receive, from the core network, anindication that the device is registered with the core network based onproviding the PPP NAS uplink transport indication of execution of thesecurity mode command.
 20. The non-transitory computer-readable mediumof claim 15, wherein the one or more instructions, that cause the one ormore processors to establish the first PDU session with the corenetwork, cause the one or more processors to: provide a PPP non-accessstratum (NAS) first PDU session establishment request to the corenetwork; receive a PPP NAS first PDU session accept message from thecore network based on providing the PPP NAS first PDU sessionestablishment request, wherein the PPP NAS first PDU session acceptmessage includes a first session identifier for the first PDU session;establish the first PDU session with the core network based on receivingthe PPP NAS first PDU session accept message from the core network; andprovide a PPP NAS first PDU session establishment complete indication tothe core network based on establishing the first PDU session with thecore network.